Package | ca.on.oh-cms |
Type | StructureDefinition |
Id | Id |
FHIR Version | R4 |
Source | https://simplifier.net/resolve?scope=ca.on.oh-cms@1.0.2-alpha1.0.2&canonical=http://ehealthontario.on.ca/fhir/StructureDefinition/ca-on-cms-profile-Patient |
Url | http://ehealthontario.on.ca/fhir/StructureDefinition/ca-on-cms-profile-Patient |
Version | 1.0.0 |
Status | draft |
Name | CMSPatient |
Experimental | False |
Description | The elements marked as MustSupport ('S' in a red box) must be supported if the data is present in the sending system. Please click here for the details. |
Type | Patient |
Kind | resource |
No resources found
StructureDefinition | |
http://ehealthontario.ca/fhir/StructureDefinition/ext-id-health-card-version-code | HCNVersionCode |
Note: links and images are rebased to the (stated) source
{
"resourceType" : "StructureDefinition",
"text" : {
"status" : "empty",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\" />"
},
"url" : "http://ehealthontario.on.ca/fhir/StructureDefinition/ca-on-cms-profile-Patient",
"version" : "1.0.0",
"name" : "CMSPatient",
"status" : "draft",
"description" : "The elements marked as MustSupport ('S' in a red box) must be supported if the data is present in the sending system. Please <a href= \"https://www.hl7.org/fhir/conformance-rules.html#mustSupport\" target=\"blank\">click here </a> for the details.",
"fhirVersion" : "4.0.1",
"kind" : "resource",
"abstract" : false,
"type" : "Patient",
"baseDefinition" : "http://hl7.org/fhir/StructureDefinition/Patient",
"derivation" : "constraint",
"differential" : {
"element" : [
{
"id" : "Patient.meta",
"path" : "Patient.meta",
"min" : 1,
"mustSupport" : true
},
{
"id" : "Patient.meta.profile",
"path" : "Patient.meta.profile",
"comment" : "#### **_` FOR CMS USAGE: The meta.profile = http://ehealthontario.ca/fhir/StructureDefinition/ca-on-cms-profile-Patient|1.0.0 `_**\r\nIt is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set.",
"min" : 1,
"mustSupport" : true
},
{
"id" : "Patient.identifier",
"path" : "Patient.identifier",
"comment" : "#### **_`FOR CMS USAGE: For Patient.identifier, Ontario Health Card Number (HCN) and Medical Record Number (MRN) are supported. In case of Ontario HCN, the identifier.system = \"https://fhir.infoway-inforoute.ca/NamingSystem/ca-on-patient-hcn\". In case of MRN, identifier.system should be the corresponding MRN of the healthcare facility. CMS will reject the request upon receiving multiple Ontario HCNs.`_**",
"min" : 1,
"mustSupport" : true
},
{
"id" : "Patient.identifier.extension:data-absent-reason",
"path" : "Patient.identifier.extension",
"sliceName" : "data-absent-reason",
"type" : [
{
"code" : "Extension",
"profile" : [
"http://hl7.org/fhir/StructureDefinition/data-absent-reason"
]
}
],
"mustSupport" : true
},
{
"id" : "Patient.identifier.extension:hCNVersionCode",
"path" : "Patient.identifier.extension",
"sliceName" : "hCNVersionCode",
"max" : "1",
"type" : [
{
"code" : "Extension",
"profile" : [
"http://ehealthontario.ca/fhir/StructureDefinition/ext-id-health-card-version-code"
]
}
],
"mustSupport" : true,
"isModifier" : false
},
{
"id" : "Patient.identifier.system",
"path" : "Patient.identifier.system",
"mustSupport" : true
},
{
"id" : "Patient.identifier.value",
"path" : "Patient.identifier.value",
"mustSupport" : true
},
{
"id" : "Patient.name",
"path" : "Patient.name",
"min" : 1,
"constraint" : [
{
"key" : "ele-2",
"severity" : "error",
"human" : "SHALL atleast contain a family name or text",
"expression" : "family.exist() or text.exist()"
}
],
"mustSupport" : true
},
{
"id" : "Patient.name.text",
"path" : "Patient.name.text",
"mustSupport" : true
},
{
"id" : "Patient.name.family",
"path" : "Patient.name.family",
"mustSupport" : true
},
{
"id" : "Patient.name.given",
"path" : "Patient.name.given",
"definition" : "#### **_` FOR CMS USAGE: It is recommended to provide Patient's First Name in the first instance and the Middle Name(s) in the subsequent instances. CMS doesn't impose any limitations on the number of repetitions but recommends to align with Provincial Client Registry. `_**",
"mustSupport" : true
},
{
"id" : "Patient.telecom",
"path" : "Patient.telecom",
"mustSupport" : true
},
{
"id" : "Patient.telecom.system",
"path" : "Patient.telecom.system",
"min" : 1,
"mustSupport" : true
},
{
"id" : "Patient.telecom.value",
"path" : "Patient.telecom.value",
"min" : 1,
"mustSupport" : true
},
{
"id" : "Patient.gender",
"path" : "Patient.gender",
"min" : 1,
"mustSupport" : true
},
{
"id" : "Patient.birthDate",
"path" : "Patient.birthDate",
"min" : 1,
"mustSupport" : true
},
{
"id" : "Patient.deceased[x]",
"path" : "Patient.deceased[x]",
"mustSupport" : false
},
{
"id" : "Patient.address",
"path" : "Patient.address",
"mustSupport" : true
},
{
"id" : "Patient.address.use",
"path" : "Patient.address.use",
"mustSupport" : true
},
{
"id" : "Patient.address.type",
"path" : "Patient.address.type",
"mustSupport" : true
},
{
"id" : "Patient.address.line",
"path" : "Patient.address.line",
"definition" : "This component contains the house number, apartment number, street name, street direction, P.O. Box number, delivery hints, and similar address information.\r\n\r\n#### **_` FOR CMS USAGE: It's recommended to have 4 lines and each line to have a limit of 80 characters. `_**",
"mustSupport" : true
},
{
"id" : "Patient.address.city",
"path" : "Patient.address.city",
"mustSupport" : true
},
{
"id" : "Patient.address.state",
"path" : "Patient.address.state",
"mustSupport" : true
},
{
"id" : "Patient.address.postalCode",
"path" : "Patient.address.postalCode",
"mustSupport" : true
},
{
"id" : "Patient.address.country",
"path" : "Patient.address.country",
"mustSupport" : true
},
{
"id" : "Patient.photo",
"path" : "Patient.photo",
"definition" : "Image of the patient.\r\n\r\n#### **_` FOR CMS USAGE: The default cardinality is retained for this element. However, the current CMS Specification doesn't support any use-case to support photos due to their size and storage restrictions. `_**"
}
]
}
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.